README FOR DEMONSTRATION MULTIMEDIA VIEWER PUBLISHING TOOLKIT 2.0 --------------------------------------------------- PTK SETUP ========= This section provides more information about the SETUP program in the Viewer 2.0 Publisher's Toolkit. INSTALLING OVER A BETA INSTALLATION ----------------------------------- If you have installed a Beta release of Multimedia Viewer, it is recommended that you remove the Multimedia Viewer PTK program group before you install the current release of Viewer. Otherwise, the Viewer SETUP program installs a new, duplicate icon for the Viewer Gallery. COPYING NEW VERSIONS OF FILES ----------------------------- If you reinstall the Viewer PTK over an existing installation and Setup finds existing files with the same date/time stamp in the directory to which you're installing, it does not display "Copying file..." messages for the files it installs over the existing files. (You will notice activity on your hard disk while Viewer installs the files from the CD-ROM.) GRAPHICS FILTERS INSTALLED WITH VIEWER 2.0 ------------------------------------------ To ensure the correct operation of the Convert tool, the Viewer 2.0 SETUP program installs versions of the standard graphics filters supplied with other Microsoft applications (including Word for Windows and PowerPoint). It installs these filters if you install the Multimedia Viewer authoring tools, but only if it detects that the filters provided in the Viewer 2.0 PTK have more recent version numbers than the filters on your machine. If you have other versions of these filters on your machine, the WIN.INI file may contain entries for these filters that point to directories other than the MSAPPS\GRPHFLT subdirectory of your Windows directory. (These entries are in the [MS Graphic Import Filters] and [MS Graphic Export Filters] sections of WIN.INI.) The Viewer 2.0 SETUP program does not change these WIN.INI entries. If these entries cause problems when you try to run Convert or other applications that use the filters, remove them and then reinstall the authoring tools for the Viewer 2.0 PTK. DEVICE INTERACTIONS =================== This section describes devices and device drivers that are known to cause problems with Viewer 2.0. VIDEO PROBLEMS -------------- In some situations, Viewer titles may encounter video display problems when using high resolution video drivers from various video card manufacturers. This problem can often be fixed by obtaining updated drivers from your video card manufacturer. Make sure the video drivers you are using were designed to be compatible with Microsoft Windows version 3.1. Contact the manufacturer of your video card for updated Windows display drivers. Their phone number should be in the manuals that came with your video card or personal computer. Another option for obtaining updated drivers is the Microsoft Download service, an electronic bulletin board that can be accessed via a modem at (206) 936-MSDL (6735). Drivers provided on the Microsoft Supplemental Driver Library (MSDL) are compressed with the PKWare utilities, and are in the form of executable files (.EXE extension). It is best to download the file or files you need into an empty directory on your hard disk, or to a blank formatted floppy. To decompress these drivers after downloading them, either: >From Windows File Manager: double click on the filename (e.g., the appropriate file ending in .EXE) that you downloaded; or, >From the DOS prompt: change to the directory containing the downloaded file, type the filename, and press ENTER; An alternative to obtaining a new or updated display driver is to change your video mode to a standard video mode such as 640 x 480 resolution, with as many colors as your video card can support at that resolution. To use your title while waiting for an updated video driver from your video card manufacturer, you can use the standard VGA driver that comes with Windows. This display mode is only 16 colors and some images may not look as well as they would in 256 colors. Also, image display takes slightly longer when running in 16 color mode. For instructions on installing the standard VGA driver, please see Help within Windows Setup in the Main program group in the Program Manager. ATI ULTRA GRAPHICS ADAPTER -------------------------- You may encounter problems in Viewer titles if you are not using the most current video driver for the ATI Ultra graphics adapter. Some of the problems known to be caused by earlier versions of the driver include: - Displaying TrueType fonts larger than 20 points incorrectly - Repainting the desktop bitmap incorrectly after closing a title - Problems creating hot spots in 2-color bitmaps in Hotspot Editor - Banding problems in bitmaps when displayed in 1,024-by-768 mode - Problems displaying certain extended characters on the menu bar See the previous section, "Video Problems," for more information about obtaining updated versions of the device driver for this video adapter. PRINTERS THAT USE UNIDRV.DLL ---------------------------- Some printers require the installation of a DLL named UNIDRV.DLL. Printers that use this DLL may encounter problems when printing topics from Viewer titles. To work around this problem, choose Print Setup and clear the Color check box (ordinarily, this box is checked during the default setup.) DEC ETHERWORKS TURBO /TP NETWORK ADAPTER ---------------------------------------- Problems may arise when you compile a title over a network using the DEC Etherworks Turbo /TP network adapter. VIEWER COMPILER =============== This section provides additional information about the Viewer compiler and indexer. ERROR MESSAGES -------------- Error 8041, "Entry/Exit macro specification overflow," may also indicate that the project file includes too many topic groups. AUTHORING AND AUTHORING TOOLS ============================= This section provides additional information about authoring subjects, including authoring tools such as Project Editor, Topic Editor, and Hotspot Editor. PARAGRAPH FORMATTING IN POPUP TOPICS ------------------------------------ Right paragraph margins are ignored in popups. To create right-side white space in a popup, enclose the topic paragraphs in a table (the right margin values of the paragraphs in the tables will be used). FIELD STATEMENTS IN NONSCROLLING PARAGRAPHS ------------------------------------------- By default, text in nonscrolling paragraphs (formatted Keep With Next) are assigned field value 1. You can assign different field values (using {vfld} statements) to text in nonscrolling regions. However, doing this excludes the text from "Topic Titles Only" searches. LIMITS ON TOPIC-ENTRY COMMAND FOOTNOTES --------------------------------------- Topic-entry commands for a topic have a combined limit of 512 characters. XA FILE NAMES FOR SONY PLAYER TITLES ------------------------------------ In titles for the Sony Multimedia CD-ROM Player, filenames for XA streams cannot begin with a pound sign (#). Using this character may interfere with playback of the XA stream because the Mammoth player interprets this character as a "resume" command rather than part of the filename. USING #IGNORE AND #ENDIGNORE STATEMENTS IN PROJECT EDITOR --------------------------------------------------------- As noted in pages 12-10 and 12-11 of the Authoring Guide, you can type #ignore and #endignore statements as entries in the RTF and Baggage cards in Project Editor. These statements comment out a series of filenames located between the #ignore and #endignore statements. EXERCISE CAUTION WHEN USING THESE STATEMENTS IN PROJECT EDITOR! As noted in the Authoring Guide, you MUST include a matching #endignore statement for any #ignore statement. If you type a #ignore statement without a matching #endignore statement, and then save the project file, Project Editor will assume that everything following the #ignore statement (including material outside the [FILES] or [BAGGAGE] section) is to be ignored. When you reopen the .MVP file in Project Editor, you might see the contents of other project file sections moved into the RTF or Baggage cards. Also, Project Editor will attempt to recreate the missing sections by adding empty (and duplicate) entries. If this happens, you'll need to open the project file in Word and manually fix the errors. CITATION IN [OPTIONS] - TITLE OPTIONS DIALOG BOX ------------------------------------------------ Project Editor lets you type a SHIFT+ENTER keystroke when typing the citation text. However, this writes a newline character to the project file, resulting in a project-file error (compiler error 2131, Invalid Options Syntax). Do not press SHIFT+ENTER when editing this field. BUILD EXPRESSION IN [OPTIONS] - COMPILER OPTIONS DIALOG BOX ----------------------------------------------------------- Project Editor lets you type a SHIFT+ENTER keystroke when typing the build expression. However, this writes a newline character to the project file, resulting in a project-file error (compiler error 2131, Invalid Options Syntax). Do not press SHIFT+ENTER when editing this field. CLOSE SOURCE FILES BEFORE COMPILING ----------------------------------- Before compiling a title from Project Editor, be sure to close all source files. If .RTF files are still open in Word, your title will fail to compile. COMMAND PARAMETER EDITING ------------------------- When editing string parameters in the edit command dialog box, Topic Editor highlights the parameters, including the quotes ( ` and ' ). When typing in a new string parameter, be sure to include the required quotes. WINDOWS, PANES, AND POPUPS LIMITATION ------------------------------------- The maximum number of windows, panes, and popups that Project Editor allows you to define is approximately 153 total (windows, panes, and popups combined). However, the actual Viewer limit is 255 for each type: 255 windows, 255 panes, and 255 popups. If you wish to define more windows, panes, and popups than Project Editor will allow, edit the .MVP file without using Project Editor. VIEWER RUNTIME AND DLLS ======================= This section provides additional information about the Viewer runtime (MVIEWER2.EXE) and its associated search and multimedia DLLs. RUNNING VIEWER TITLES UNDER WINDOWS 3.0 --------------------------------------- The standard Search dialog box is not supported under Windows 3.0. You can write your own custom search interface. Also, the French and German versions of the Viewer runtime files do not support Windows 3.0. VIEWER EDIT/COPY COMMAND ------------------------ The Copy command on Viewer's Edit menu immediately copies text to the Clipboard. Users do not need to choose the OK button. As a result, this command overwrites the current contents of the Clipboard whenever users select it. The Viewer command CopyDialog() has the same effect. SEARCH HITS IN TABLES --------------------- Search hits may be incompletely highlighted if they appear in the last column of a table and when the paragraph in which the word appears is the first in its row. WORD STEMMING ON 80286-BASED MACHINES ------------------------------------- If your title will be run on 80286-based machines, do not use word stemming. USING METAFILES WITH VIEWER 2.0 ------------------------------- Viewer 2.0 can display metafiles created by the filter programs in Word for Windows 2.0. The Convert utility uses these same filters, so metafiles created by Convert can be used with Viewer 2.0. Older versions of some applications create metafiles in a format incompatible with Viewer 2.0. These metafiles may also cause problems with other programs in the Viewer 2.0 package (for example, with Hotspot Editor). If a metafile causes problems when you try to build or display a Viewer title, convert it to standard DIB format. Converting metafiles to DIB format also may improve display performance in the title. Metafiles with palettes cannot be displayed using {bmx} commands. MCI BAGGAGE FILES IN WINDOWS NT ------------------------------- Viewer 2.0 has not been fully tested on Windows NT. Viewer titles that are viewed under Windows NT cannot open MCI files (such as waveforms or Video for Windows files) that are stored in baggage. Viewer titles that will be displayed on NT should store all MCI files external to the .MVB file. PLAYING VIDEO FOR WINDOWS FILES ------------------------------- The driver necessary to play .AVI files is included in this package. You may ship this driver with your title. However, you must purchase Microsoft Video for Windows to obtain the tools necessary to prepare .AVI files. CREATING VIEWER TITLE SETUPS ============================ This section lists notes about creating setup programs for titles and the Viewer 2.0 files you can include with your titles. EXTENDED CHARACTERS IN TITLE.MST FILE ------------------------------------- In the TITLE.MST file, extended characters cannot be used in the names assigned to ProgManGroup$ or ProgManItem$. Extended characters used this way may not appear as part of the group name or item name when SETUP creates the program group and adds the title to the group. FILES YOU CAN DISTRIBUTE WITH VIEWER TITLES ------------------------------------------- You can modify any of the following files provided with Viewer 2.0 and ship them as part of your own titles: mvhlpusa\*.* mvhlpfrn\*.* mvhlpger\*.* mvsample\progsamp\setup\*.* mvsample\progsamp\eplist\*.* mvsample\progsamp\katasrch\*.* You can ship any of the following files as part of a Viewer for Windows title: mvsysusa\*.* mvsysfrn\*.* mvsysger\*.* You can ship the following files with Viewer titles for the Sony MMCD Player only with a licensing agreement from Microsoft; see the application enclosed in the Viewer 2.0 PTK for details: mvsony\exeme.exe mvsony\viewer.vid